Update Newtonsoft.Json to be same version across all projects #5158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Resolved merge confilct |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
yao-msft
reviewed
Feb 6, 2025
yao-msft
approved these changes
Feb 7, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the NuGet management tools in Visual Studio,
Newtonsoft.Jsonhad different versions being used across different projects within the solution. This PR bumps them all to the same version, moving some from13.0.2up to13.0.3. In the cases where the version specification was added, it is due to the package being a transient dependencyMicrosoft Reviewers: Open in CodeFlow